| Package | hl7.ehrs.ehrsfmr21 |
| Type | Requirements |
| Id | Id |
| FHIR Version | R5 |
| Source | http://hl7.org/ehrs/https://build.fhir.org/ig/mvdzel/ehrsfm-fhir-r5/Requirements-EHRSFMR2.1-AS.1.7.html |
| Url | http://hl7.org/ehrs/Requirements/EHRSFMR2.1-AS.1.7 |
| Version | 2.1.0 |
| Status | active |
| Date | 2024-11-26T16:30:50+00:00 |
| Name | AS_1_7_Manage_Practitioner_Patient_Relationships |
| Title | AS.1.7 Manage Practitioner/Patient Relationships (Function) |
| Experimental | False |
| Realm | uv |
| Authority | hl7 |
| Description | Identify relationships among providers treating a single patient, and provide the ability to manage patient lists assigned to a particular provider. |
| Purpose | This function addresses the ability to manage current information about the relationships between providers and the patients. This information should be able to flow seamlessly between the different components of the system, and between the EHR system and other systems. Business rules may be reflected in the presentation of, and the access to this information. The relationship among providers treating a single patient will include any necessary chain of authority/responsibility. Example: - In a care setting with multiple providers, where the patient can only see certain kinds of providers (or an individual provider); allow the selection of only the appropriate providers. - The user is presented with a list of people assigned to a given practitioner and may alter the assignment as required to a group, to another individual or by sharing the assignment. |
No resources found
No resources found
Note: links and images are rebased to the (stated) source
Identify relationships among providers treating a single patient, and provide the ability to manage patient lists assigned to a particular provider.
This function addresses the ability to manage current information about the relationships between providers and the patients. This information should be able to flow seamlessly between the different components of the system, and between the EHR system and other systems. Business rules may be reflected in the presentation of, and the access to this information. The relationship among providers treating a single patient will include any necessary chain of authority/responsibility.
Example:
| AS.1.7#01 | SHALL |
The system SHALL provide the ability to extract the information needed to identify all providers by name associated with a specific patient encounter. |
| AS.1.7#02 | SHALL |
The system SHALL provide the ability to tag the role of each provider associated with a patient (e.g., encounter provider, primary care provider, attending, resident, or consultant). |
| AS.1.7#03 | MAY |
The system MAY provide the ability to tag the role of each provider associated with a patient using structured data. |
| AS.1.7#04 | SHALL |
The system SHALL provide the ability to capture the list of providers who have been associated with a specific episode of care for a patient (i.e., all the providers who have participated in a specific episode of care (which could include multiple encounters)). |
| AS.1.7#05 | SHOULD |
The system SHOULD provide the ability to capture and maintain, as discrete data elements, the identity of providers who have been associated with a specific patient encounter. |
| AS.1.7#06 | SHOULD |
The system SHOULD provide the ability for an authorized user to capture and maintain information on the relationship of a provider to a patient. |
| AS.1.7#07 | SHOULD |
The system SHOULD provide the ability to render patient lists by provider. |
| AS.1.7#08 | SHALL |
The system SHALL provide the ability to tag primary or principal provider(s) responsible for the care of a patient within a care setting. |
| AS.1.7#09 | SHOULD |
The system SHOULD provide the ability to capture and maintain, as structured data elements, the principal provider responsible for the care of an individual patient. |
FHIR{
"resourceType" : "Requirements",
"id" : "EHRSFMR2.1-AS.1.7",
"meta" : {
"profile" : [
"http://hl7.org/ehrs/StructureDefinition/FMFunction"
]
},
"text" : {
"status" : "extensions",
"div" : "<div xmlns=\"http://www.w3.org/1999/xhtml\">\n <span id=\"description\"><b>Statement <a href=\"https://hl7.org/fhir/versions.html#std-process\" title=\"Normative Content\" class=\"normative-flag\">N</a>:</b> <div><p>Identify relationships among providers treating a single patient, and provide the ability to manage patient lists assigned to a particular provider.</p>\n</div></span>\n\n \n <span id=\"purpose\"><b>Description <a href=\"https://hl7.org/fhir/versions.html#std-process\" title=\"Informative Content\" class=\"informative-flag\">I</a>:</b> <div><p>This function addresses the ability to manage current information about the relationships between providers and the patients. This information should be able to flow seamlessly between the different components of the system, and between the EHR system and other systems. Business rules may be reflected in the presentation of, and the access to this information. The relationship among providers treating a single patient will include any necessary chain of authority/responsibility.</p>\n<p>Example:</p>\n<ul>\n<li>In a care setting with multiple providers, where the patient can only see certain kinds of providers (or an individual provider); allow the selection of only the appropriate providers.</li>\n<li>The user is presented with a list of people assigned to a given practitioner and may alter the assignment as required to a group, to another individual\nor by sharing the assignment.</li>\n</ul>\n</div></span>\n \n\n \n\n \n <span id=\"requirements\"><b>Criteria <a href=\"https://hl7.org/fhir/versions.html#std-process\" title=\"Normative Content\" class=\"normative-flag\">N</a>:</b></span>\n \n <table id=\"statements\" class=\"grid dict\">\n \n <tr>\n <td style=\"padding-left: 4px;\">\n \n <span>AS.1.7#01</span>\n \n </td>\n <td style=\"padding-left: 4px;\">\n \n \n \n <span>SHALL</span>\n \n </td>\n <td style=\"padding-left: 4px;\" class=\"requirement\">\n \n <span><div><p>The system SHALL provide the ability to extract the information needed to identify all providers by name associated with a specific patient encounter.</p>\n</div></span>\n \n \n </td>\n </tr>\n \n <tr>\n <td style=\"padding-left: 4px;\">\n \n <span>AS.1.7#02</span>\n \n </td>\n <td style=\"padding-left: 4px;\">\n \n \n \n <span>SHALL</span>\n \n </td>\n <td style=\"padding-left: 4px;\" class=\"requirement\">\n \n <span><div><p>The system SHALL provide the ability to tag the role of each provider associated with a patient (e.g., encounter provider, primary care provider, attending, resident, or consultant).</p>\n</div></span>\n \n \n </td>\n </tr>\n \n <tr>\n <td style=\"padding-left: 4px;\">\n \n <span>AS.1.7#03</span>\n \n </td>\n <td style=\"padding-left: 4px;\">\n \n \n \n <span>MAY</span>\n \n </td>\n <td style=\"padding-left: 4px;\" class=\"requirement\">\n \n <span><div><p>The system MAY provide the ability to tag the role of each provider associated with a patient using structured data.</p>\n</div></span>\n \n \n </td>\n </tr>\n \n <tr>\n <td style=\"padding-left: 4px;\">\n \n <span>AS.1.7#04</span>\n \n </td>\n <td style=\"padding-left: 4px;\">\n \n \n \n <span>SHALL</span>\n \n </td>\n <td style=\"padding-left: 4px;\" class=\"requirement\">\n \n <span><div><p>The system SHALL provide the ability to capture the list of providers who have been associated with a specific episode of care for a patient (i.e., all the providers who have participated in a specific episode of care (which could include multiple encounters)).</p>\n</div></span>\n \n \n </td>\n </tr>\n \n <tr>\n <td style=\"padding-left: 4px;\">\n \n <span>AS.1.7#05</span>\n \n </td>\n <td style=\"padding-left: 4px;\">\n \n \n \n <span>SHOULD</span>\n \n </td>\n <td style=\"padding-left: 4px;\" class=\"requirement\">\n \n <span><div><p>The system SHOULD provide the ability to capture and maintain, as discrete data elements, the identity of providers who have been associated with a specific patient encounter.</p>\n</div></span>\n \n \n </td>\n </tr>\n \n <tr>\n <td style=\"padding-left: 4px;\">\n \n <span>AS.1.7#06</span>\n \n </td>\n <td style=\"padding-left: 4px;\">\n \n \n \n <span>SHOULD</span>\n \n </td>\n <td style=\"padding-left: 4px;\" class=\"requirement\">\n \n <span><div><p>The system SHOULD provide the ability for an authorized user to capture and maintain information on the relationship of a provider to a patient.</p>\n</div></span>\n \n \n </td>\n </tr>\n \n <tr>\n <td style=\"padding-left: 4px;\">\n \n <span>AS.1.7#07</span>\n \n </td>\n <td style=\"padding-left: 4px;\">\n \n \n \n <span>SHOULD</span>\n \n </td>\n <td style=\"padding-left: 4px;\" class=\"requirement\">\n \n <span><div><p>The system SHOULD provide the ability to render patient lists by provider.</p>\n</div></span>\n \n \n </td>\n </tr>\n \n <tr>\n <td style=\"padding-left: 4px;\">\n \n <span>AS.1.7#08</span>\n \n </td>\n <td style=\"padding-left: 4px;\">\n \n \n \n <span>SHALL</span>\n \n </td>\n <td style=\"padding-left: 4px;\" class=\"requirement\">\n \n <span><div><p>The system SHALL provide the ability to tag primary or principal provider(s) responsible for the care of a patient within a care setting.</p>\n</div></span>\n \n \n </td>\n </tr>\n \n <tr>\n <td style=\"padding-left: 4px;\">\n \n <span>AS.1.7#09</span>\n \n </td>\n <td style=\"padding-left: 4px;\">\n \n \n \n <span>SHOULD</span>\n \n </td>\n <td style=\"padding-left: 4px;\" class=\"requirement\">\n \n <span><div><p>The system SHOULD provide the ability to capture and maintain, as structured data elements, the principal provider responsible for the care of an individual patient.</p>\n</div></span>\n \n \n </td>\n </tr>\n \n </table>\n</div>"
},
"url" : "http://hl7.org/ehrs/Requirements/EHRSFMR2.1-AS.1.7",
"version" : "2.1.0",
"name" : "AS_1_7_Manage_Practitioner_Patient_Relationships",
"title" : "AS.1.7 Manage Practitioner/Patient Relationships (Function)",
"status" : "active",
"date" : "2024-11-26T16:30:50+00:00",
"publisher" : "EHR WG",
"contact" : [
{
"telecom" : [
{
"system" : "url",
"value" : "http://www.hl7.org/Special/committees/ehr"
}
]
}
],
"description" : "Identify relationships among providers treating a single patient, and provide the ability to manage patient lists assigned to a particular provider.",
"jurisdiction" : [
{
"coding" : [
{
"system" : "http://unstats.un.org/unsd/methods/m49/m49.htm",
"code" : "001",
"display" : "World"
}
]
}
],
"purpose" : "This function addresses the ability to manage current information about the relationships between providers and the patients. This information should be able to flow seamlessly between the different components of the system, and between the EHR system and other systems. Business rules may be reflected in the presentation of, and the access to this information. The relationship among providers treating a single patient will include any necessary chain of authority/responsibility.\n\nExample:\n- In a care setting with multiple providers, where the patient can only see certain kinds of providers (or an individual provider); allow the selection of only the appropriate providers.\n- The user is presented with a list of people assigned to a given practitioner and may alter the assignment as required to a group, to another individual\n or by sharing the assignment.",
"statement" : [
{
"extension" : [
{
"url" : "http://hl7.org/ehrs/StructureDefinition/requirements-dependent",
"valueBoolean" : false
}
],
"key" : "EHRSFMR2.1-AS.1.7-01",
"label" : "AS.1.7#01",
"conformance" : [
"SHALL"
],
"conditionality" : false,
"requirement" : "The system SHALL provide the ability to extract the information needed to identify all providers by name associated with a specific patient encounter.",
"derivedFrom" : "EHR-S_FM_R1.1 S.3.4#1"
},
{
"extension" : [
{
"url" : "http://hl7.org/ehrs/StructureDefinition/requirements-dependent",
"valueBoolean" : false
}
],
"key" : "EHRSFMR2.1-AS.1.7-02",
"label" : "AS.1.7#02",
"conformance" : [
"SHALL"
],
"conditionality" : false,
"requirement" : "The system SHALL provide the ability to tag the role of each provider associated with a patient (e.g., encounter provider, primary care provider, attending, resident, or consultant).",
"derivedFrom" : "EHR-S_FM_R1.1 S.3.4#2"
},
{
"extension" : [
{
"url" : "http://hl7.org/ehrs/StructureDefinition/requirements-dependent",
"valueBoolean" : false
}
],
"key" : "EHRSFMR2.1-AS.1.7-03",
"label" : "AS.1.7#03",
"conformance" : [
"MAY"
],
"conditionality" : false,
"requirement" : "The system MAY provide the ability to tag the role of each provider associated with a patient using structured data."
},
{
"extension" : [
{
"url" : "http://hl7.org/ehrs/StructureDefinition/requirements-dependent",
"valueBoolean" : false
}
],
"key" : "EHRSFMR2.1-AS.1.7-04",
"label" : "AS.1.7#04",
"conformance" : [
"SHALL"
],
"conditionality" : false,
"requirement" : "The system SHALL provide the ability to capture the list of providers who have been associated with a specific episode of care for a patient (i.e., all the providers who have participated in a specific episode of care (which could include multiple encounters)).",
"derivedFrom" : "EHR-S_FM_R1.1 S.3.4#3"
},
{
"extension" : [
{
"url" : "http://hl7.org/ehrs/StructureDefinition/requirements-dependent",
"valueBoolean" : false
}
],
"key" : "EHRSFMR2.1-AS.1.7-05",
"label" : "AS.1.7#05",
"conformance" : [
"SHOULD"
],
"conditionality" : false,
"requirement" : "The system SHOULD provide the ability to capture and maintain, as discrete data elements, the identity of providers who have been associated with a specific patient encounter."
},
{
"extension" : [
{
"url" : "http://hl7.org/ehrs/StructureDefinition/requirements-dependent",
"valueBoolean" : false
}
],
"key" : "EHRSFMR2.1-AS.1.7-06",
"label" : "AS.1.7#06",
"conformance" : [
"SHOULD"
],
"conditionality" : false,
"requirement" : "The system SHOULD provide the ability for an authorized user to capture and maintain information on the relationship of a provider to a patient.",
"derivedFrom" : "EHR-S_FM_R1.1 S.3.4#4"
},
{
"extension" : [
{
"url" : "http://hl7.org/ehrs/StructureDefinition/requirements-dependent",
"valueBoolean" : false
}
],
"key" : "EHRSFMR2.1-AS.1.7-07",
"label" : "AS.1.7#07",
"conformance" : [
"SHOULD"
],
"conditionality" : false,
"requirement" : "The system SHOULD provide the ability to render patient lists by provider.",
"derivedFrom" : "EHR-S_FM_R1.1 S.3.4#5"
},
{
"extension" : [
{
"url" : "http://hl7.org/ehrs/StructureDefinition/requirements-dependent",
"valueBoolean" : false
}
],
"key" : "EHRSFMR2.1-AS.1.7-08",
"label" : "AS.1.7#08",
"conformance" : [
"SHALL"
],
"conditionality" : false,
"requirement" : "The system SHALL provide the ability to tag primary or principal provider(s) responsible for the care of a patient within a care setting.",
"derivedFrom" : "EHR-S_FM_R1.1 S.3.4#6"
},
{
"extension" : [
{
"url" : "http://hl7.org/ehrs/StructureDefinition/requirements-dependent",
"valueBoolean" : false
}
],
"key" : "EHRSFMR2.1-AS.1.7-09",
"label" : "AS.1.7#09",
"conformance" : [
"SHOULD"
],
"conditionality" : false,
"requirement" : "The system SHOULD provide the ability to capture and maintain, as structured data elements, the principal provider responsible for the care of an individual patient."
}
]
}
XIG built as of ??metadata-date??. Found ??metadata-resources?? resources in ??metadata-packages?? packages.